home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970929-19971216
/
000155_news@newsmaster….columbia.edu _Tue Oct 21 08:13:35 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
5KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id IAA05149
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 21 Oct 1997 08:13:35 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id IAA10167
for kermit.misc@watsun; Tue, 21 Oct 1997 08:13:34 -0400 (EDT)
Path: news.columbia.edu!news.new-york.net!news-peer.gsl.net!news.gsl.net!gip.net!news-peer.sprintlink.net!news-sea-19.sprintlink.net!news-in-west.sprintlink.net!news.sprintlink.net!Sprint!204.122.16.44!news.eskimo.com!jimo
From: jimo@eskimo.com (Jim Osborn)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: login script beeps unexpectedly
Date: 21 Oct 1997 04:04:59 GMT
Organization: Eskimo North (206) For-Ever
Lines: 96
Message-ID: <62h9lb$pbm$1@eskinews.eskimo.com>
References: <62ejvl$fpk$1@eskinews.eskimo.com> <62ft4g$j94$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: eskimo.com
Xref: news.columbia.edu comp.protocols.kermit.misc:7933
In article <62ft4g$j94$1@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>In article <62ejvl$fpk$1@eskinews.eskimo.com>,
>Jim Osborn <jimo@eskimo.com> wrote:
>: I use the following macro to connect with my ISP...
>:
>And which Kermit program are you using?
Oops, sorry - C-Kermit 6.0, purchased on the CD about three weeks ago,
running on a Linux console, kernel 1.1.59. Thought my mention of
the CK60 manual said it all. :)
>: ... and to reject the
>: one line of theirs I know to be unreliable, restarting the dialing
>: process if I detect that line. I'd like the thing to beep at me
>: when it eventually connects, so I know to drop whatever else I'm
>: doing, but to stay quiet otherwise.
>:
>: For some reason, this macro beeps every time it finds the bad modem
>: and restarts. Can someone explain why?
>:
>It's not obvious from your script, but if INPUT ECHO is ON, and if the
>service sends a beep character, then Kermit will echo it.
I guessed that, so I double checked, and the ISP sends no beeps.
I watched a cycle of at least five toxic modem offers, and got a beep
on each cycle, so I'm pretty confident it's not a simple buffering
issue, per your comments below. That is, it's not flushing a beep
from a prior login attempt. When I say "beep" I'm really referring
to the "echo \007" command, of course.
>: One minor question: can someone explain the difference between the
>: apparently undocumented "beep" command (can't find reference to it
>: in the CK60 book, other than its use in a script example)...
>:
>It's on page 40, but you're right, it's missing from the index.
Ah, so it is; I'll add it to my marginal index. :)
>It just rings the bell or beeps, whatever your console is set up to
>do normally when it gets an ASCII BEL character.
>
>: and the
>: good old "echo \007" command? The effects are very different.
>:
>So you must be using Kermit 95. In this case, the BEEP command can produce
>different sounds...
Nope, Unix. That's what was so surprising. Back when I wrote one of
my first shell scripts, sometime in 1982, called "beep" it consisted of:
echo -n "\007"
>:...
>: define eskimo {
>: while not defined \%1 {
>: askq \%1 {Eskimo Password: }
>: }
>: :retry
>: dial 258-0759
>: in 30 {Your Selection ==>} #Initial selector, choose service
>: output 1\13 #Select Eskimo
>: in 60 login: #Start login process
>: out jimo\13 #Look for: Hello ,CLI,,27,xxx@seattle2
>: clear input
>: in 30 {Welcome to eskimo.com} #Read Annex ID string
>: xif \find({CLI,,27},\v(input)) { #Start over if toxic modem
>: xif \find({@seattle2},\v(input)) {
>: echo {Aborting 27,,2}
>: goto retry
>: }
>: }
>: in 30 Password:
>: out \%1\13
>: in 60 {Main Command?}
>: out {!} #Start shell
>: # beep #doesn't beep until escape back to kermit
>: echo \007 #^G
>: connect /quietly
>: }
>
>"doesn't beep until escape back to kermit" is evidently a bug. It's one of
>those buffering things -- you tell the system to write something and it says
>"OK I wrote it", but it really just put it in a list of things to do, which
>evidently it does not get around to doing until something else forces it to.
>We'll see if we can find a way to make the system force the beep out
>immediately. In the meantime "echo \007" is a good workaround (James Bond
>to the rescue?).
Thanks for the response, and a terrific program! If you can think of
any workaround for the unwanted beep, I'd love to impliment it. Maybe
one of these days I'll dive into the source code for "beep" and see
just how it differs from my old shell script, for curiosity. As you say,
that question has a solid workaround.
Jim